collection

Introduction

This document describes the test steps required to assess a mobile device’s capability to synchronize calendar data with a calendar store (referred to from now on as “the server”).

It is provided as a resource for implementers to help promote interoperability, but the successful execution of the test cases described herein should not be considered as any type of formal validation.

The tests described in this document are to be manually executed. Data synchronization sessions will be initiated between the mobile device under test and the server. A desktop or web based calendar client should be used to enter and verify data on the server.

The testing method used will be a black box testing approach, wherein inputs will be provided from both the server and device and outputs will be generated. Comparisons between the actual output and the expected output will determine the capability of the device to synchronize calendar data.

The test cases have been written with the understanding that some form of synchronization is occurring, but they make no assumptions concerning the underlying methodology. They can be used for testing OMA Data Synchronization (formerly SyncML) implementations, cable based synchronization solutions, or even mobile clients which reconcile a local store using CalDAV (or their own proprietary protocol). It should also be possible to test direct data transfer between devices using short link connectivity protocols such as Bluetooth or Infrared with minimal changes.

The test cases assume that the underlying data exchange formats used will be iCalendar and vCard 3.0.

It is possible to use these test cases with implementations that use vCalendar 1.0, vCard 2.1, or some other proprietary format. Arguments supporting the importance of iCalendar to the Mobile Industry are discussed in the Consortium white paper on The Benefits of iCalendar for the Mobile Industry.

The intent of this test suite is to verify the validity of the calendar data that is exchanged and to guarantee that the calendar user has an accurate representation of their calendar regardless of which side (mobile device or server) they are viewing it from.

It does not attempt to go beyond this scope, so it does not include tests for such things as:

  • Conflict Resolution

  • Correct protocol usage (e.g. support for OMA DS Server Alerted Notification or Suspend/Resume)

  • Stress tests for a large volume of calendar events

  • Stress tests for calendar event content, such as very long DESCRIPTION properties (e.g. copying full text of an email into the calendar description)

  • Effects experienced when multiple synchronization technologies are used in parallel (e.g. duplicate entry problems reported when using Palm HotSync or BlackBerry clients and OMA DS in conjunction)

  • Negative test conditions. In other words, incorrect input data that deliberately generates errors such as invalid recurrence patterns

Each group of tests starts with basic test cases to verify that essential calendaring data can be transferred back and forth accurately. These are followed by tests that focus on aspects that have been identified as problem areas.

Some test cases identify problem areas for further discussion at a forthcoming CalConnect Mobile Interoperability Test Event. These ‘Birds of a Feather’ discussion items are marked with ‘BOF Topic‘ in the text. References to external specifications are shown in the text in square brackets.

A complete list of limitations and current omissions within this test suite are documented in Appendix C.